Access Point Connectivity

ABSTRACT

A method that includes determining, at a mobile device, that a count of encounters by the mobile device with an access point fails to satisfy a threshold. The access point is associated with a first network. The method also includes establishing a connection with a second network in response to determining the count fails to satisfy the threshold. The access point is unassociated with the second network.

CLAIM OF PRIORITY

The present application is a continuation of, and claims priority to,U.S. patent application Ser. No. 14/863,625, filed on Sep. 24, 2015,which is a continuation of U.S. patent application Ser. No. 13/895,878,filed on May 16, 2013, issued as U.S. Pat. No. 9,167,509, which is acontinuation of U.S. patent application Ser. No. 12/939,258, filed onNov. 4, 2010, issued as U.S. Pat. No. 8,467,361; each of theabove-referenced applications is incorporated herein by reference in itsentirety.

FIELD OF THE DISCLOSURE

This disclosure relates generally to the field of wireless access pointnotification.

BACKGROUND

Mobile devices are used in a variety of locations where wireless accessof a network can be available to the mobile devices. In one example,wireless access of the Internet, via one or more access points, can beavailable to a mobile device operated by a user, and the mobile devicecan convey information associated with the one or more access points tothe user. In the past, mobile devices displayed all service setidentifiers (SSIDs) of all access points within range of the mobiledevices which can be or become disturbing and/or annoying to users.

BRIEF DESCRIPTION OF THE DRAWINGS

The preferred embodiments will become apparent upon reading thefollowing detailed description and upon reference to the accompanyingdrawings in which:

FIG. 1 and FIG. 2 provide block diagrams of one or more networkcommunication systems, according to one or more embodiments;

FIG. 3 provides a block diagram of a mobile device, according to one ormore embodiments;

FIG. 4 provides a block diagram of a wireless access point, according toone or more embodiments;

FIG. 5 illustrates a diagram of a mobile device and a portion of a userof the mobile device, according to one or more embodiments;

FIG. 6 provides a diagram of a menu usable to configure a mobile device,according to one or more embodiments;

FIG. 7 and FIG. 8 provide diagrams of menus usable to manage one or moreconnections of a mobile device to one or more wireless access points,according to one or more embodiments; and

FIGS. 9-12 illustrate methods of operating a mobile device.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Itshould be understood, however, that the drawings and detaileddescription thereto are not intended to limit the disclosure to theparticular form disclosed, but on the contrary, the disclosure is tocover all modifications, equivalents and alternatives falling within thespirit and scope of an invention as defined by appended claims.

DETAILED DESCRIPTION

FIG. 1 illustrates a block diagram of one or more network communicationssystems, according to one or more embodiments. As shown, mobile devices(MDs) 1040-1042 and a wireless access points (APs) 1030 and 1031 can beat a location 1050; MDs 1043 and 1044 and a wireless access point (AP)1034 can be at a location 1051; and a mobile device (MD) 1045, awireless AP 1035, a network 1012, and a modem 1076 can be at a location1052. In one or more embodiments, locations 1050-1052 can include one ormore of hotels, homes, businesses, airports, restaurants, geographicregions, planes, trains, automobiles, and coffee shops, among others.

In one or more embodiments, a wireless AP can communicate with one ormore computing devices (e.g., MDs 1040-1045) in a wireless fashion. Forexample, a wireless AP can communicate with one or more computingdevices (e.g., MDs 1040-1045) using one or more of Institute ofElectrical and Electronics Engineers (IEEE) 802.16, WiMax, IEEE 802.11,WiFi (e.g., wireless Ethernet), IEEE 802.15 (e.g., Bluetooth), IEEE802.15.4, ZigBee, 6LoWPAN, ultra wide band, and/or infraredcommunication technologies, among others. In one or more embodiments, awireless access point can include a transceiver to communicate with oneor more computing devices using one or more wireless methods, processes,and/or protocols.

In one or more embodiments, wireless APs 1030-1035 can respectivelytransmit one or more signals 1060-1065. In one or more embodiments, theone or more signals transmitted from a wireless AP (e.g., one or moresignals 1060 transmitted from wireless AP 1030) can includeidentification information. For example, wireless AP 1030 can be awireless AP that implements one or more portions of IEEE 802.11, andwireless AP 1030 can transmit one or more signals 1060 that can includeidentification information that can include one or more of a service setidentifier (SSID) and a basic service set identifier (BSSID). In one ormore embodiments, the one or more signals 1060-1065 can includerespective beacons that can include the respective identificationinformation usable to identify respective wireless APs 1030-1035.

In one or more embodiments, one or more of the one or more signals1060-1065 and/or one or more of wireless APs 1030-1035 can utilize oneor more ISM (industrial, scientific and medical) bands to communicateinformation to and/or from one or more of MDs 1040-1045. For example, anISM band can include an electromagnetic signal frequency range of6.765-6.795 MHz, 433.05-434.79 MHz, 902-928 MHz, 2.4-2.5 GHz,5.725-5.875 GHz, or 24.0-24.25 GHz, among others. In one or moreembodiments, an ISM band can be used in identifying a wireless AP.

In one or more embodiments, the one or more signals transmitted from thewireless AP can be received by one or more MDs. In one example, one ormore of MDs 1040-1042 can receive one or more signals 1060 from wirelessAP 1030, and one or more of MDs 1040-1042 can utilize identificationinformation included in one or more signals 1061 to identify wireless AP1031. In a second example, one or more of MDs 1043 and 1044 can utilizeidentification information included in one or more signals 1064 toidentify wireless AP 1034, and MD 1045 can utilize identificationinformation included in one or more signals 1065 to identify wireless AP1035. In one or more embodiments, a MD can convey identification of awireless AP to a user of the MD. For example, MD 1040 can identifywireless AP 1030 via the identification information included in one ormore signals 1060 and convey identification of wireless AP 1030 to auser of MD 1040. For instance, MD 1040 can convey identification ofwireless AP 1030 to the user of MD 1040 via a pop-up window or menu.

In one or more embodiments, a MD can convey identification of a wirelessAP to a user of the MD after a number of instances that the wireless APhas been encountered. For example, an instance that wireless AP 1030 hasbeen encountered can include a first period of time of receiving theidentification information included in one or more signals 1060 followedby a second period of time of not receiving the identificationinformation included in one or more signals 1060. For instance, MD 1040can be transported out of a range that MD 1040 can utilize one or moresignals 1060. For example, MD 1040 can be transported from location 1050to a location 1052 which can be out of a range that MD 1040 can utilizeone or more signals 1060.

In one or more embodiments, the second period of time can include anamount of time transpiring during which another instance of encounteringa wireless AP may not be counted, enumerated, and/or started. Forexample, MD 1042 may be close to and/or proximate to a range that MD1042 can utilize one or more signals 1060. For instance, the range thatMD 1042 can utilize one or more signals 1060 may be two hundred feet,and MD 1042 may be transported within location 1050 such that MD 1042 iswithin the two hundred foot range and outside the two hundred foot rangewithin the second period of time. In one or more embodiments, MD 1042may not count, enumerate, and/or start another instance of encounteringwireless AP 1030 during the second period of time to discriminatelymeasure a number of times that wireless AP 1030 has been encountered.For example, the amount of time transpiring may be ten minutes orlonger, and by discriminately measuring the number of times thatwireless AP 1030 has been encountered by MD 1042 may not be misleading,since MD 1042 has been transported in and out of the range that MD 1042can utilize one or more signals 1060 during the amount of timetranspiring.

In one or more embodiments, one or more MDs can receive one or moresignals that convey identification of a wireless AP which may not beincluded at one or more locations that includes the one or more MDs. Inone example, one or more of MDs 1040-1042, at location 1050, can receiveone or more signals 1062 that can include identification informationassociated with wireless AP 1032. In a second example, one or more ofMDs 1043 and 1044, at location 1051, can receive the one or more signals1062 and/or one or more signals 1063 that can include identificationinformation associated with respective wireless APs 1032 and 1033. Inanother example, MDs 1043 and 1044, at location 1051, can receive theone or more signals 1061 that can include identification informationassociated with wireless AP 1031, at location 1050.

In one or more embodiments, MDs 1040, 1042, and 1045 can be wirelesslycoupled to respective wireless APs 1030, 1031, and 1035. In one example,MDs 1040, 1042, and 1045 can be wirelessly coupled to respectivewireless APs 1030, 1031, and 1035 after MDs 1040, 1042, and 1045identify respective wireless APs 1030, 1031, and 1035 a respectivenumber of instances. As illustrated, wireless APs 1030 and 1031 can becoupled to a network 1010 that can be coupled to a network managementdevice (NMD) 1020. In one or more embodiments, MDs 1040 and 1042 can becoupled to network 1010 via respective wireless APs 1030 and 1031, andMD 1045 can be coupled to a network 1012 via wireless AP 1035. As shown,network 1010, wireless AP 1032, wireless AP 1033, a network 1011, and anetwork 1012 can be coupled to a network 1014 via NMD 1020, a router1070, a modem 1072, a router 1074, and a modem 1076, respectively, andwireless APs 1034 and 1035 can be respectively coupled to networks 1011and 1012.

In one or more embodiments, MDs 1041 and 1044 can be coupled to andcommunicate with a network 1013. In one example, MD 1041 may not havecounted and/or enumerated a number of instances of identifying one ormore of wireless APs 1030 and 1031. In a second example, MD 1041 may nothave counted and/or enumerated a number of instances of identifyingwireless AP 1030 and have counted and/or enumerated a number ofinstances of identifying wireless AP 1031 but a configuration and/ordata structure of MD 1041 may not permit MD 1041 to communicate withwireless AP 1031. In another example, MD 1041 may not have countedand/or enumerated a number of instances of identifying wireless AP 1034.

In one or more embodiments, network 1013 can be and/or implement atelecommunications network. For instance, network 1013 can be and/orimplement a wireless telecommunications network that can support one ormore wireless telecommunications network protocols such as one or moreof General Packet Radio Service (GPRS), enhanced data rates for GSMevolution (EDGE), long tem′ evolution (LTE), CDMA (code divisionmultiple access), TDMA (time division multiple access), and/or FDMA(frequency division multiple access), among others. In one or moreembodiments, network 1013 can be coupled to and/or include a telephonynetwork that can include a wireless cellular telecommunications networkand/or a wireless satellite telecommunications network. In one or moreembodiments, the telephony network can communicate information such asvoice and/or data.

In one or more embodiments, network 1013 can implement and/or provideaccess and/or services of one or more other networks. For example,network 1013 can provide access and/or services of a public network(e.g., the Internet) to one or more of MDs 1040-1045 via one or morebase transceiver stations and/or one or more satellites. In one or moreembodiments, one or more antennas of a base transceiver station can bemounted on a roof of a building, on a mast, on a tower (e.g., a cellulartelephone communications tower), and/or on a side of a structure (e.g.,a building, a parking garage, a lamp post, etc.). In one or moreembodiments, access to these other networks can include one or more“services” these other networks may provide. In one or more embodiments,the one or more services can utilize, be associated with, and/orcorrespond to one or more protocols of one or more computer and/orsoftware applications. In one or more embodiments, network 1013 providesaccess and/or services of one or more other networks at a lower datarate than network 1014 can provide to one or more of MDs 1040-1045. Forexample, network 1013 can include less bandwidth than network 1014. Inone or more embodiments, network 1014 can provide access and/or servicesof one or more other networks to MDs 1040-1045 via one or more wirelessAPs 1030-1035, one or more routers 1070 and 1074, one or more modems1072 and 1076, and/or one or more network management devices (NMDs) suchas NMD 1020.

In one or more embodiments, access to one or more of networks 1013 and1014 can include one or more “services” these networks may provide. Forexample, these one or more services can include one or more of: email,world wide web, file transfer, printing, file sharing, file systemsharing, remote file system, network file system (NFS), news, multicast,netbios, encryption, domain name service (DNS), routing, tunneling, chatsuch as Internet Remote Chat and/or AOL Instant Messenger, gaming,licensing, license management, digital rights management, network time,remote desktop, remote windowing, audio, database (e.g., Oracle,Microsoft SQL Server, PostgreSQL, etc.), authentication, accounting,authorization, virtual local area network (VLAN) (e.g., IEEE 802.1q),virtual private network or VPN, audio, phone, Voice Over InternetProtocol (VoIP), paging, and video, among others. In one or moreembodiments, the one or more service can be associated with and/orcorrespond to one or more protocols of one or more computer and/orsoftware applications.

In one or more embodiments, NMD 1020 can provide authentication, qualityof service (QoS), communication traffic shaping, and/or access controlfrom one or more computing devices (e.g., MDs 1040 and 1042) coupled tonetwork 1010 through one of APs 1030 and 1031 to network 1014. Forexample, NMD 1020 can include an access control list that can bemodifiable, and NMD 1020 can use the access control list to permitand/or deny access of one or more computing devices (e.g., MDs 1040 and1042) to network 1014. In one or more embodiments, NMD 1020 can performone or more processes and/or methods that can modify the access controllist. In one or more embodiments, NMD 1020 can receive one or moresignals from a remote signaling device, and the access control list ofNMD 1020 can be modified based on the received one or more signals fromthe remote signaling device. In one or more embodiments, signals and/orsignaling can be used in communicating establishment and/or control ofcommunications and/or access to a network and/or resources of thenetwork. In one or more embodiments, signals and/or signaling can beused between two different network providers or between two systems of asingle network provider. In one example, a first network provider can beor include a second network provider, and signals and/or signaling canbe used between the first network provider and the second networkprovider can mean signaling between two systems of the first networkprovider. In one or more embodiments, signals and/or signaling can beused to convey information (e.g., configuration messages, accountingmessages, control data, etc.) that is different than user informationtransfer (e.g., a telephone conversation between two users, a textmessage communication between two users, etc.).

In one or more embodiments, networks 1010, 1011, 1012, and/or network1014 can include a wired network, a wireless network or a combination ofwired and wireless networks. Networks 1010, 1011, 1012, and/or network1014 can include and/or be coupled to various types of communicationsnetworks, such as a public switched telephone network (PSTN), anInternet, a wide area network (WAN) (e.g., a private WAN, a corporateWAN, a public WAN, etc.), a local area network (LAN). In one or moreembodiments, NMD 1020 can be coupled to a PSTN, e.g., Ethernet cable andDSL; a cable (television) based network; a satellite-based system;and/or a fiber based network; among others. In one or more embodiments,networks 1010, 1011, 1012, and/or network 1014 can include one or morewireless networks, e.g., based on IEEE 802.11 and/or IEEE 802.16. Forinstance, one or more of APs 1030 and 1031 can be coupled to network1010 in a wireless fashion. Networks 1010, 1011, 1012, and/or network1014 can include one or more DSL (digital subscriber line) and/or cable(e.g., cable television) networks and/or infrastructures. For example,networks 1010, 1011, 1012, and/or network 1014 can include one or moreof: cable modems, cable modem termination systems (CMTSs), satellitemodems, DSL modems, digital subscriber line access multiplexers(DSLAMs), broadband remote access servers (BRASs), telecommunicationscircuits, and/or metropolitan area networks (MANs), among others. In oneor more embodiments, network 1014 may form part of the Internet, or maycouple to other networks, e.g., other local or wide area networks suchas the Internet. In one or more embodiments, NMD 1020 can be a systemoperable to include one or more of network 1010, wireless AP 1030,wireless AP 1031, and/or various networking equipment, among others.

In one or more embodiments, each MD of MDs 1040-1045 can include and/orcan be coupled to one or more transceivers that allow the MD tocommunicate with network 1013 and one or more of wireless APs 1030-1035.For example, MD 1041 can include or be coupled to a first transceiverthat can communicate with network 1013 and include or be coupled to asecond transceiver to communicate with wireless AP 1030. For instance,MD 1041 can include or be coupled to a first transceiver that cancommunicate with one or more a base transceiver station and a satelliteof or coupled to network 1013 and include or be coupled to a secondtransceiver, such as a wireless Ethernet transceiver, to communicatewith wireless AP 1030.

Turning now to FIG. 2, a block diagram of one or more networkcommunications systems, according to one or more embodiments. Each ofthe elements illustrated in FIG. 2 is described with reference toFIG. 1. As illustrated, one or more of MDs 1040-1045 can be transportedfrom a first location to a second location. For example: MD 1040 can betransported from location 1050 to location 1052; MD 1041 can betransported from location 1050 to location 1051; MD 1042 can betransported from location 1050 to location 1052; MD 1043 can betransported from location 1051 to location 1050; MD 1044 can betransported from location 1051 to location 1050; and MD 1045 can betransported from location 1052 to location 1050.

In one or more embodiments, MDs 1043, 1044, and 1040 can be wirelesslycoupled to respective wireless APs 1030, 1031, and 1035. In one example,MDs 1043, 1044, and 1040 can be wirelessly coupled to respectivewireless APs 1030, 1031, and 1035 after MDs 1043, 1044, and 1040identify respective wireless APs 1030, 1031, and 1035 a respectivenumber of instances.

In one or more embodiments, MDs 1042 and 1045 can be coupled to andcommunicate with a network 1013. In one example, MD 1045 may not havecounted and/or enumerated a number of instances of identifying one ormore of wireless APs 1030 and 1031. In a second example, MD 1045 may nothave counted and/or enumerated a number of instances of identifyingwireless AP 1030 and have counted and/or enumerated a number ofinstances of identifying wireless AP 1031 but a configuration and/ordata structure of MD 1045 may not permit MD 1045 to communicate withwireless AP 1031. In another example, MD 1042 may not have countedand/or enumerated a number of instances of identifying wireless AP 1035.

In one or more embodiments, location 1052 can be or be included in avehicle. For example, location 1052 can be or be included in a plane,train, or automobile, and location 1052 can move from one point toanother point at one or more speeds and/or directions. For instance, oneor more of MDs 1040 and 1042 can receive identification informationassociated with one or more of wireless APs 1030-1034 via respective oneor more signals 1060-1064 when in a range to utilize such one or moresignals.

Turning now to FIG. 3, a block diagram of a mobile device isillustrated, according to one or more embodiments. As shown, MD 1040 caninclude a memory 3020 coupled to a processor 3010, and MD 1040 caninclude one or more network interfaces 3030 and 3031, user outputinterface 3040, and/or user input interface 3050 coupled to processor3010. In one or more embodiments, memory 3020 can include one or moreapplications (APPs) 3070-3072 and/or operating system (OS) 3075 that caninclude instructions executable by processor 3010 to implement one ormore methods and/or one or more systems associated with MD 1040. In oneor more embodiments, OS 3075 can include one or more structures and/orfunctionalities describe with reference to one or more of APPs3070-3072. In one or more embodiments, memory 3020 can include aconfiguration (config) 3080 that can include one or more configurationsand/or one or more user preferences usable in operation of MD 1040and/or to implement one or more methods and/or one or more systemsassociated with MD 1040. In one or more embodiments, MD 1040 may be anyof various types of devices, including a computer system, a portablecomputer system, a tablet computer system, a personal digital assistant(PDA), a mobile telephone (e.g., a wireless telephone, a cellulartelephone, a satellite telephone, etc.), a wearable computing device, anInternet appliance, a communications device, or wireless device.

In one or more embodiments, user output interface 3040 can be used toconvey information (e.g., text, graphics, video, audio, etc.) to a userof MD 1040. For example, MD 1040 may include a display (e.g., a displayscreen) that can be used to convey text, graphic, and/or videoinformation to a user of MD 1040. In one or more embodiments, MD 1040can include a sound output device 3042 coupled to user output interface3040. In one or more embodiments, sound output device 3042 can include adevice and/or circuitry that can produce one or more sounds.

In one or more embodiments, a sound can be an alteration in pressure, analteration particle displacement, and/or an alteration particle velocitythat can be propagated in one or more elastic mediums. In one or moreembodiments, a sound can be a superposition of one or more propagatedalterations of pressure, particle displacement, and/or velocity that canbe propagated in one or more elastic mediums, and one or more sounds canpropagate through the one or more elastic mediums via one or more soundwaves. In one or more embodiments, an intensity of a sound wave can besound energy transmitted, and an intensity of a sound field can be soundenergy transmitted per a time period through an area perpendicular to adirection of transmission at a point in a coordinate system. Forexample, an intensity of a sound field can be measured in ergs persecond per centimeters squared.

In one or more embodiments, sound output device 3042 can include a bodythat can produce vibrations to create one or more sounds. For instance,sound output device 3042 can include a speaker that can produce one ormore sounds, audible to a user of MD 1040, by vibrating a body (e.g., adiaphragm, a crystal, a ceramic, etc.).

In one or more embodiments, user output interface 3040 can be coupled toa sound output device 3044. In one instance, sound output device 3044can include one or more of an amplifier and/or a speaker. In anotherinstance, sound output device 3044 can include one or more earphones. Inone or more embodiments, user output interface 3040 can be coupled tosound output device 3044 in a wired fashion. In one or more embodiments,user output interface 3040 can be coupled to sound output device 3044 ina wireless fashion. In one example, user output interface 3040 cancommunicate sound information to output device 3044 using an ISM band.For instance, user output interface 3040 can communicate soundinformation to output device 3044 using one or more of a personal arenetwork (PAN), IEEE 802.15, IEEE 802.15.4, ZigBee, 6LoWPAN, frequencymodulation of a carrier wave, amplitude modulation of a carrier wave,light signals, and serial pulses, among others. In one or moreembodiments, sound output device 3044 can be or be included in a devicethat includes IEEE 802.15 receiver or transceiver, such as a Bluetoothheadset or earpiece.

In one or more embodiments, user input interface can be used to receiveuser input from a user of MD 1040. In one example, MD 1040 may include akeyboard that can be used to receive user input from a user of MD 1040.In another example, MD 1040 may include a one or more sensors that canbe used to receive user input from a user of MD 1040. In one instance,one or more sensors can include resistive sensors that can be used todetermine one or more positions on a display screen. In anotherinstance, one or more sensors can include capacitive sensors that can beused to determine one or more positions on a display screen. In one ormore embodiments, user output interface 3040 and user input interfacecan be used to implement a keyboard. For example, user output interface3040 can be used to present an image of a keyboard, and user inputinterface 3050 can receive a position of user input on the image of thekeyboard to determine a received key of the keyboard. In one or moreembodiments, MD 1040 can include a sound input device 3052 coupled touser input interface 3050.

In one or more embodiments, a sound input device can include a deviceand/or circuitry that can receive one or more sounds and transform theone or more sounds into one or more electrical signals (e.g., voltageand/or current). In one or more embodiments, a sound input device caninclude an acoustic to electric transducer or senor that can convert oneor more sounds into one or more electrical signals. For example, theacoustic to electric transducer or senor can include a body (e.g., adiaphragm, a crystal, a ceramic, etc.) that can vibrate in response toone or more sounds (e.g., in response to sound pressure), and movementof the body can be transformed and/or converted into one or moreelectrical signals. For instance, a sound input device can include amicrophone. In one or more embodiments, a microphone can use one or moreof capacitance change (e.g., a condenser microphone), electromagneticinduction (e.g., a dynamic microphone), piezoelectric generation, andlight modulation to produce one or more electrical signal from one ormore mechanical vibrations.

In one or more embodiments, user input interface 3050 can be coupled toa sound input device 3054. In one instance, sound input device 3054 caninclude one or more of an amplifier and/or a microphone. In one or moreembodiments, user input interface 3050 can be coupled to sound inputdevice 3054 in a wired fashion. In one or more embodiments, user inputinterface 3050 can be coupled to sound input device 3054 in a wirelessfashion.

In one example, sound input device 3054 can communicate soundinformation to user input interface 3050 with using an ISM band. Forinstance, sound input device 3054 can communicate sound information touser input interface 3050 using one or more of a PAN, IEEE 802.15, IEEE802.15.4, ZigBee, 6LoWPAN, frequency modulation of a carrier wave,amplitude modulation of a carrier wave, light signals, and serialpulses, among others. In one or more embodiments, sound input device3054 can be or be included in a device that includes IEEE 802.15transmitter or transceiver, such as a Bluetooth headset or microphone.

In one or more embodiments, network interface 3030 can be used to coupleMD 1040 to network 1013, and MD 1040 can use network interface 3030 tocommunicate information (e.g., data, voice data, etc.) with network1013. For example, network interface 3030 can include a transceiver thatis operable to communicate information with network 1013. In one or moreembodiments, network interface 3030 can include a subscriber identitymodule (SIM) 3060. In one or more embodiments, SIM 3060 can securelystore an international mobile subscriber identity (IMSI) which caninclude a unique number and/or identity associated with a global systemfor mobile communications (GSM) network and/or a universal mobiletelecommunications system (UMTS) network. In one example, the uniquenumber and/or identity can be used to determine informationcorresponding to MD 1040 from a home location register (HLR) and/or froma visitor location register (VLR). In one or more embodiments, a MSISDN(mobile subscriber ISDN (integrated services digital network) number,mobile station international ISDN number(s), or mobile internationalISDN number) can be a number that can uniquely identify a subscriptionin a GSM mobile network and/or a UMTS (universal mobiletelecommunications system) mobile network. For example, the MSISDN caninclude a telephone number corresponding to SIM 3060. In one instance,the MSISDN can include a country code, a national destination code, anda subscriber number. In another instance, the MSISDN can include acountry code, a number planning area, and a subscriber number.

In one or more embodiments, SIM 3060 can be embodied in a removable card(e.g., a SIM card) that can be removed from a first MD associated with afirst subscriber account and placed in a second MD, so that the secondMD can be associated with the first subscriber account. For example, SIM3060 embodied as a SIM card can be associated with a first subscriberaccount and used in MD 1040, thereby associating MD 1040 with the firstsubscriber account; SIM 3060 can be removed from MD 1040, therebydisassociating MD 1040 with the first subscriber account; and SIM 3060can be placed in MD 1041, thereby associating MD 1041 with the firstsubscriber account.

In one or more embodiments, network interface 3031 can be used tocommunicate with a wireless AP. For example, network interface 3031 canbe used to communicate with wireless AP 1030. In one or moreembodiments, network interface 3031 can include a transceiver that isoperable to communicate information with wireless AP 1030.

In one or more embodiments, MD 1040 can include a position device 3080coupled to processor 3010. In one example, position device 3080 caninclude a global positioning system (GPS) receiver. In another example,position device 3080 can include a terrestrial radio navigation systemreceiver such as LORAN (LOng RAngeNavigation). In one or moreembodiments, position device 3080 can provide one or more services suchas one or more of positioning, navigation, and timing to processor 3010.For example, a positioning service can provide one or more of latitudeinformation, longitude information, altitude information, and accuracyinformation (e.g., a radius of uncertainty for a geographic location orposition). In one or more embodiments, one or more of wireless MDs1041-1045 can include same and/or similar one or more structures and/orone or more functionalities as described with reference to MD 1040.

In one or more embodiments, the term “memory” can mean a “memory medium”and/or “computer readable memory medium” which is intended to includevarious types of memory or storage, including an installation medium,e.g., a CD-ROM, or floppy disks, a random access memory or computersystem memory such as DRAM, SRAM, EDO RAM, Rambus RAM, NVRAM, EPROM,EEPROM, flash memory etc., and/or a non-volatile memory such as amagnetic media, e.g., a hard drive, and/or optical storage. The memorymedium can include other types of memory as well, or combinationsthereof. In one or more embodiments, the memory medium can be and/orinclude an article of manufacture and/or a software product. Inaddition, the memory medium can be located in a first computer in whichthe programs are executed, or can be located in a second differentcomputer and/or hardware memory device that connects to the firstcomputer over a network. In one or more embodiments, the second computerprovides the program instructions to the first computer for execution.The memory medium can also be a distributed memory medium, e.g., forsecurity reasons, where a portion of the data is stored on one memorymedium and the remaining portion of the data can be stored on adifferent memory medium. Also, the memory medium can include one of thenetworks to which the current network is coupled, e.g., a SAN (StorageArea Network).

In one or more embodiments, each of the systems described herein maytake various forms, including a personal computer system, servercomputer system, workstation, network appliance, Internet appliance,wearable computing device, personal digital assistant (PDA), tabletcomputing device, laptop, mobile telephone, mobile multimedia device,embedded computer system, television system, and/or other device. Ingeneral, the terms “computing device”, “computer”, and/or “computersystem” can be broadly defined to encompass any device having aprocessor which executes instructions from a memory medium. In one ormore embodiments, the memory medium in one or more systems can store asoftware program and/or data for performing and/or enabling processesand/or methods described herein. In one or more embodiments, a CPU orprocessing unit in one or more systems executing code and data from amemory medium includes a means for executing one or more softwareprogram according to the methods and/or flowcharts described herein.

Turning now to FIG. 4, a block diagram of a wireless access point isillustrated, according to one or more embodiments. As shown, wireless AP1030 can include a memory medium 4020 coupled to a processor 4010, andwireless AP 1030 can include one or more network interfaces 4030 and4031 coupled to processor 4010.

In one or more embodiments, a network interface (e.g., network interface4030) can be coupled to a network, a router, or a modem, among others.In one example, network interface 4030 can implement an Ethernetinterface that is operable to be coupled to a gateway device, where thegateway device is operable to be coupled to network 1014. In anotherexample, network interface 4030 can implement a WiMax network interfacethat is operable to be coupled to a WiMax access point that is operableto be coupled to network 1014. In one or more embodiments, a networkinterface (e.g., network interface 4031) can be coupled to one or moreMDs in a wireless fashion. In one example, network interface 4031 canimplement an IEEE 802.11 interface that can wirelessly communicate withone or more MDs. In a second example, network interface 4031 canimplement an IEEE 802.16 interface that can wirelessly communicate withone or more MDs. In another example, network interface 4031 canimplement a wireless USB interface that can wireless communicate withone or more MDs.

As shown, memory medium 4020 can include one or more APPs 4070-4072and/or an OS 4075 that can store data and/or instructions executable byprocessor 4010 to implement one or more systems, processes, and/ormethods associated with wireless AP 1030. As illustrated, memory medium4020 can include identification information (ID info) 4080 associatedwith wireless AP 1030. In one or more embodiments, the one or moresignals 1060 can include identification information 4080 or can includeinformation based on identification information 4080 which can be usedto identify wireless AP 1030. In one or more embodiments, networkinterface 4031 can implement one or more portions of at least one ofIEEE 802.16, WiMax, IEEE 802.11, IEEE 802.15, IEEE 802.15.4, ZigBee,6LoWPAN, ultra wide band, and an infrared communication protocol. Forexample, network interface 4031 can implement one or more portions ofIEEE 802.11, and network interface 4031 can transmit one or more signals1060 that can include identification information that can include one ormore of a SSID, a BSSID, an Internet protocol (IP) address, a WEP (wiredequivalence privacy) code, and a WiFi protected access (WPA) code, amongothers.

In one instance, identification information 4080 can include informationthat can be used to produce one or more of the SSID, the BSSID, the WEPcode, and the WPA code. In another instance, identification information4080 can include one or more of the SSID, the BSSID, the IP address, theWEP code, and the WPA code, among others. In one or more embodiments,identification information 4080 can include one or more strings ofcharacters that can be or can be used in one or more of the SSID, theBSSID, the IP address, the WEP code, and the WPA code, among others. Inone example, a string of characters utilized in the SSID can include“CupOfJoe”, and location 1050 can include the Cup of Joe Coffee Shop. Inanother example, a string of characters utilized in the WPA code caninclude “RikerOmega3!!!”.

In one or more embodiments, the BSSID can include an address of networkinterface 4031. For example, the BSSID can include a media accesscontrol (MAC) address of network interface 4031. In one instance, theBSSID can be stored in network interface 4031. In another instance, theBSSID can be stored in identification information 4080. In one or moreembodiments, a MAC address can be a unique identifier of a networkinterface. In one example, the MAC address can be assigned by amanufacturer of the network interface. In another example, the MACaddress can be configured by software (e.g., overriding an addressassigned by a manufacturer). In one or more embodiments, the MAC addresscan include a 48-bit address or number. In one or more embodiments, theMAC address can include a 64-bit address or number. In one or moreembodiments, a network address, such as a MAC address among othernetwork addresses, can include other lengths or sizes.

It is noted that the IEEE expects that 48-bit MAC address will beexhausted no sooner than the year 2100 Anno Domini. Accordingly, a48-bit may be considered substantially unique (e.g., few duplications)after some point in the future, according to one or more embodiments. Inone or more embodiments, 64-bit MAC addresses can be used in one or moreof IPv6 (Internet protocol version six), ZigBee, IEEE 802.15.4, and6LoWPAN, among others. In one or more embodiments, one or more ofwireless APs 1031-1035 can include same and/or similar one or morestructures and/or one or more functionalities as described withreference to wireless AP 1030.

Turning now to FIG. 5, a diagram of a mobile device and a portion of auser of the mobile device are illustrated, according to one or moreembodiments. As shown, MD 1040 can include one or more user selectablebuttons 5010-5016. In one or more embodiments, buttons 5010-5016 can becoupled to input interface 3050. MD 1040 can include a touch screen 5020that can be coupled to output interface 3040 and input interface 3050.As illustrated, icons 5030-5054 can be displayed by touch screen 5020.In one or more embodiments, icons 5030-5036 can represent files, icons5040-5044 can represent applications (e.g., applications 3070-3072), andicons 5050-5054 can represent folders (e.g., folders or directories of afile system). In one or more embodiments, one or more of icons 5030-5054can be selected by a digit (e.g., a finger) 5060 or other appendage of auser of MD 1040 and/or one or more of icons 5030-5054 can be selected bya stylus (not shown). In one or more embodiments, one or more of icons5030-5054 can be selected by a mouse or other pointing device or system.

In one or more embodiments, an icon associated with an application (APP)can be selected by user input, and the APP can be executed by MD 1040.For example, icon 5040 can be selected by user input, and APP 3070 canbe executed by MD 1040. In one or more embodiments, APP 3070 can beexecuted to configure one or more configurations and/or one or more userpreferences of MD 1040. For example, APP 3070 can access, change, and/orstore information in configuration 3080. In one or more embodiments,digit 5060 can drag an icon of icons 5030-5054 from a first portion ofscreen 5020 by selecting the icon, moving digit 5060 to a second portionof screen 5020, and removing digit 5060. In one example, digit 5060 canbe kept in contact with screen 5020 or in close proximity to screen 5020while dragging the icon. In another example, digit 5060 can select theicon, be removed from screen 5020, and select a portion of screen 5020.In one or more embodiments, digit 5060 can drag an icon an icon of icons5030-5044 to an icon of folder icons 5050-5054. In one or moreembodiments, a drag and drop process can include dragging a first iconassociated with a file or application to a second icon associated with afolder.

Turning now to FIG. 6, a diagram of a menu usable to configure a mobiledevice is illustrated, according to one or more embodiments. As shown,screen 5020 can display a menu 6010. In one or more embodiments, menu6010 can provide a user interface for APP 3070 which can be used to seta number of instances a wireless AP is encountered before wirelesslycoupling to the wireless AP and/or notifying a user of MD 1040 withinformation associated with the wireless AP.

As illustrated, menu 6010 can include one or more of a slider 6020, adisplay or text field 6030, and a selection button or icon 6040. In oneor more embodiments, slider 6020 can be selected by the user (e.g.,using digit 5060) to select the number of instances the wireless AP isencountered before wirelessly coupling to the wireless AP and/ornotifying the user of MD 1040 with information associated with thewireless AP. For example, slider 6020 can be used to transformqualitative user input into one or more quantitative values. Forinstance, slider 6020 can be used to receive user input and transformthe user input into a value of five (5) as shown by display or textfield 6030. In one or more embodiments, display or text field 6030 canbe used to accept quantitative input. For example, display or text field6030 can be selected by the user, and a keyboard can used to input aquantitative value (e.g., “5”) into display or text field 6030.

In one or more embodiments, selection button or icon 6040 can be used inreceiving user input indicating that the number of instances thewireless AP is encountered before wirelessly coupling to the wireless APand/or notifying the user of MD 1040 with information associated withthe wireless AP. For example, digit 5060 can select selection button oricon 6040, and APP 3070 can store, in configuration 3080, the number ofinstances the wireless AP is encountered before wirelessly coupling tothe wireless AP and/or notifying the user of MD 1040 with informationassociated with the wireless AP.

Turning now to FIG. 7, a diagram of a menu usable to manage one or moreconnections of a mobile device to a wireless access point isillustrated, according to one or more embodiments. As shown, screen 5020can display a menu 7010 that can include one or more buttons or icons7020-7072. In one or more embodiments, menu 7010 can provide a userinterface for APP 3070 which can be used to select a wireless AP thatwas is encountered a number of times by MD 1040. In one or moreembodiments, menu 7010 can display first identifications of respectivewireless APs that are encountered over a period of time. For example,menu 7010 can display first identifications of respective wireless APsthat are encountered over a number days (e.g., thirty days, sixty days,ninety days, etc.).

In one example, buttons or icons 7020-7023 and 7024 can display firstidentifications of respective wireless APs 1030-1032 and 1034. Forinstance, buttons or icons 7020-7022 and 7024 can display respectiveservice set identifiers (SSIDs) of respective wireless APs 1030-1032 and1034. In second example, buttons or icons 7030-7032 and 7034 can displaysecond identifications of respective wireless APs 1030-1032 and 1034.For instance, buttons or icons 7030-7032 and 7034 can display respectiveMAC addresses of respective wireless APs 1030-1032 and 1034. In one ormore embodiments, buttons or icons 7020-7022 and 7024 and/or buttons oricons 7030-7032 and 7034 can be selected by a user of MD 1040 to permitMD 1040 to communicate with respective wireless APs 1030-1032 and 1034.

In another example, one or more of buttons or icons 7040-7042 and 7044can be selected to not use or not trust one or more of respectivewireless APs 1030-1032 and 1034. In one or more embodiments, button oricon 7060 can be selected to conclude a connection process associatedwith one or more wireless APs. For example, communications via network1013 may be used rather than using a wireless AP coupled to network1014. In one or more embodiments, button or icon 7050 can be selected todisplay information associated with identifiable wireless APs withinrange of MD 1040, regardless of a number of times each wireless AP hasbeen encountered. In one or more embodiments, icon 7072 can indicatethat wireless AP 1032 uses a key, a password, and/or access code inwirelessly communicating with a MD. For example, wireless AP 1032 canuse one or more of a WEP code and a WPA code, among others.

In one or more embodiments, a wireless AP can be identified by acombination of two or more identifiers. In one example, wireless AP 1030can be identified by a combination of a SSID of “CupOfJoe” and a MACaddress of 85:26:fa:9d:b9:12. In a second example, wireless AP 1031 canbe identified by a combination of a SSID of “CupOfJoe” and a MAC addressof 85:26:fa:9d:b9:fa. In another example, wireless AP wireless AP 1034can be identified by a combination of a SSID of “LuLuCafe” and a MACaddress of aa:98:ed:93:23:78. In one or more embodiments, a wireless APcan be identified by a single identifier. In one example, wireless AP1030 can be identified by a MAC address of 85:26:fa:9d:b9:12. In asecond example, wireless AP 1031 can be identified by a MAC address of85:26:fa:9d:b9:fa. In another example, wireless AP wireless AP 1034 canbe identified by a MAC address of aa:98:ed:93:23:78.

Turning now to FIG. 8, a diagram of a menu usable to manage one or moreconnections of a mobile device to a wireless access point isillustrated, according to one or more embodiments. As shown, screen 5020can display a menu 8010 that can include one or more buttons or icons8020-8070. In one or more embodiments, menu 8010 can provide a userinterface for APP 3070 which can be used to determine whether or not touse a wireless AP that was is encountered a number of times by MD 1040.

In one example, buttons or icons 8020-8024 can display firstidentifications of respective wireless APs 1030-1034. For instance,buttons or icons 8020-8024 can display respective SSIDs of respectivewireless APs 1030-1034. In second example, buttons or icons 8030-8034can display second identifications of respective wireless APs 1030-1034.For instance, buttons or icons 8030-8034 can display respective MACaddresses of respective wireless APs 1030-1034. In one or moreembodiments, buttons or icons 8040-8044 can respectively correspond tobuttons or icons 8020-8024 and/or buttons or icons 8030-8034, andbuttons or icons 8050-8054 can respectively correspond to buttons oricons 8020-8024 and/or buttons or icons 8030-8034. In one example, oneor more of radio buttons 8040-8044 can be selected, via user input, toindicate that a respective one or more wireless APs 1030-1034 may beused in wireless communications. In another example, one or more ofradio buttons 8050-8054 can be selected, via user input, to indicatethat a respective one or more wireless APs 1030-1034 may not be used inwireless communications.

In one or more embodiments, icon or button 8060 can be selected, viauser input, to indicate that a configuration can be stored. For example,the configuration can be stored in configuration 3080 and can includeinformation that indicates whether or not a wireless AP can be used inwireless communications. For instance, the information represented viamenu 8010, which can indicate whether or not a wireless AP can be usedin wireless communications, can be stored in configuration 3080. In oneexample, wireless APs 1030, 1031, and 1034 may be used in wirelesscommunications. In one or more embodiments, wireless APs 1032 and 1033may not be used in wireless communications. In one or more embodiments,icon or button 8060 can be selected, via user input, to indicate that aconfiguration represented via menu 8010 can be stored. In one or moreembodiments, icon or button 8070 can be selected, via user input, toindicate that a configuration was not changed and/or to indicate thatany change indicated in menu 8010 can be discarded.

Turning now to FIG. 9, a method operating a mobile device isillustrated, according to one or more embodiments. At 9010, one or moresignals from a wireless AP can be received. For example, MD 1040 canreceive the one or more signals 1060 from wireless AP 1030. Forinstance, a transceiver of network interface 3031 can receive the one ormore signals 1060. At 9020, identification information can be determinedfrom the one or more signals. For example, MD 1040 can determineidentification information from the one or more signals 1060. Forinstance, the identification information can be associated with wirelessAP 1030 and/or can be used to identify wireless AP 1030. In one or moreembodiments, the identification information can include one or more of aSSID, a BSSID, a MAC address, an IP address, an ISM band, a WEP code,and a WPA code, among others.

At 9030, a wireless AP can be identified. For example, MD 1040 canidentify wireless AP 1030 via one or more of a SSID, a BSSID, a MACaddress, an IP address, an ISM band, a WEP code, and a WPA code, amongothers. At 9040, an identification of the wireless AP can be stored. Forexample, MD 1040 can store, in memory 3020, an identification ofwireless AP 1030. In one or more embodiments, storing the identificationof the wireless AP can include storing one or more portions of theidentification information determined from the received one or moresignals. For example, MD 1040 can store, in memory 3020, one or more ofa SSID, a BSSID, a MAC address, an IP address, an ISM band, a WEP code,and a WPA code determined from the one or more signals 1060.

At 9050, it can be determined whether or not an instance of encounteringthe wireless AP has concluded. In one or more embodiments, determiningwhether or not the instance of encountering the wireless AP hasconcluded can include determining whether or not wireless communicationswith the wireless AP has concluded. For example, MD 1040 may no longerwirelessly communicate with wireless AP 1030, and no longer wirelesslycommunicating with wireless AP 1030 can indicate a conclusion of theinstance that wireless AP 1030 has been encountered.

In one or more embodiments, determining whether or not the instance ofencountering the wireless AP has concluded can include determiningwhether or not the one or more signals are being received. For example,MD 1040 may no longer receive the one or more signals 1060, and nolonger receiving the one or more signals 1060 can indicate a conclusionof the instance that wireless AP 1030 has been encountered. In one ormore embodiments, the instance that wireless AP 1030 has beenencountered can include a first period of time of receiving the one ormore signals 1060 followed by a second period of time of not receivingthe one or more signals 1060. For example, determining whether or notthe instance of encountering the wireless AP has concluded can includedetermining whether or not the second period of time of not receivingthe one or more signals 1060 has transpired.

If the instance of encountering the wireless AP has not concluded,method element 9050 can be performed, according to one or moreembodiments. If the instance of encountering the wireless AP hasconcluded, information associated with the instance of encountering thewireless AP can be stored. In one example, MD 1040 can store, in memory3020, one or more of a SSID, a BSSID, a MAC address, an IP address, anISM band, a WEP code, and a WPA code, among others, associated withwireless AP 1030. In another example, MD 1040 can store, in memory 3020,one or more of a count and an enumeration of one or more instances ofencountering wireless AP 1030. For instance, can increment one or moreof a count and an enumeration, stored in memory 3020, of one or moreinstances of encountering wireless AP 1030.

Turning now to FIG. 10, a method operating a mobile device isillustrated, according to one or more embodiments. At 10010, a menu canbe displayed. For example, menu 6010 can be displayed using informationof configuration 3080. At 10020, user input can be received, where theuser input can indicate a number of instances a wireless AP isencountered before wirelessly coupling to the wireless AP and/ornotifying the user of the mobile device with information associated withthe wireless AP. At 10030, user input can be received, where the userinput can indicate that the number of instances can be stored. Forexample, the number of instances can be stored in configuration 3080.

Turning now to FIG. 11, a method operating a mobile device isillustrated, according to one or more embodiments. At 11010, a menu canbe displayed. For example, menu 7010 can be displayed using informationof configuration 3080. At 11020, user input selecting a button or iconcan be received. At 11030, a menu item selection can be determined. If abutton or icon of buttons or icons 7020-7022 and 7024 or of buttons oricons 7030-7032 and 7034 is selected, the method can proceed to 11040where the mobile device can wirelessly couple to a wireless APcorresponding to information displayed in the button or icon. If abutton or icon of buttons or icons 7040-7042 and 7044 is selected, themethod can proceed to 11050 where a configuration can be updated. Forexample, button or icon 7044 can be selected by the user input, andconfiguration 3080 can be updated such that information associated withwireless AP 1034 is not displayed by menu 7010.

If button or icon 7050 is selected, the method can proceed to 11060where screen 5020 can display information associated with one or morewireless APs that may have not been encountered at least the number oftimes specified by the user of the mobile device. In one example, screen5020 can display information associated with one or more wireless APsthat may have not been encountered at least five (5) times. In anotherexample, screen 5020 can display information associated with one or morewireless APs that may have not been encountered at least five (5) timeswithin the last thirty (30) days. If button or icon 7060 is selected,the method can proceed to 11070 where the mobile device may not wirelesscouple to a wireless AP associated with the information of menu 7010.For example, the mobile device may use network 1013 for datacommunications rather than a wireless AP associated with the informationof menu 7010.

Turning now to FIG. 12, a method operating a mobile device isillustrated, according to one or more embodiments. At 12010, a menu canbe displayed. For example, menu 8010 can be displayed using informationof configuration 3080. At 12020, user input selecting a button or iconcan be received. At 12030, a button or icon selection can be determined.If a button or icon of buttons or icons 8040-8044 is selected, themethod can proceed to 12040 where menu 8010 can be updated to indicatethat a wireless AP corresponding to the button or icon may be used. Forexample, button or icon 8040 can be selected by user input, and menu8010 can be updated to indicate that wireless AP 1030 may be used. Inone or more embodiments, the method can proceed to 12020.

If a button or icon of buttons or icons 8050-8054 is selected, themethod can proceed to 12050 where menu 8010 can be updated to indicatethat a wireless AP corresponding to the button or icon may not be used.For example, button or icon 8042 can be selected by user input, and menu8010 can be updated to indicate that wireless AP 1032 may not be used.In one or more embodiments, the method can proceed to 12020.

If button or icon 8060 is selected, a configuration can be updated at12060. For example, configuration 3080 can be updated to correspond withthe information indicated in menu 8010. If button or icon 8070 isselected, any change in menu 8010 can be discarded at 12070.

It is noted that, in one or more embodiments, one or more of the methodelements described herein and/or one or more portions of animplementation of a method element can be performed in varying orders,can be repeated, can be performed concurrently with one or more of theother method elements and/or one or more portions of an implementationof a method element, or can be omitted. Additional and/or duplicatedmethod elements can be performed as desired. For example, a processand/or method can perform one or more described method elementsconcurrently with duplicates of the one or more described methodelements. For instance, multiple methods, processes, and/or threads canbe implemented using same described method elements. In one example, MD1040 can concurrently implement some or all method elements of FIGS.9-12 for use with two or more of wireless APs 1030-1035. In one or moreembodiments, one or more of the method illustrated in FIGS. 9-12 can berepeated. For example, the method illustrated in FIG. 9 can be repeatedin multiple encounters with a single wireless AP and/or repeated inmultiple encounters with multiple wireless APs.

In one or more embodiments, concurrently can mean simultaneously. In oneor more embodiments, concurrently can mean apparently simultaneouslyaccording to some metric. For example, two or more method elementsand/or two or more portions of an implementation of a method element canbe performed such that they appear to be simultaneous to a human. It isalso noted that, in one or more embodiments, one or more of the systemelements described herein may be omitted and additional system elementscan be added as desired.

Further modifications and alternative embodiments of various aspects ofthe invention may be apparent to those skilled in the art in view ofthis description. Accordingly, this description is to be construed asillustrative only and is for the purpose of teaching those skilled inthe art the general manner of carrying out the invention. It is to beunderstood that the forms of the invention shown and described hereinare to be taken as embodiments. Elements and materials may besubstituted for those illustrated and described herein, parts andprocesses may be reversed, and certain features of the invention may beutilized independently, all as would be apparent to one skilled in theart after having the benefit of this description of the invention.Changes may be made in the elements described herein without departingfrom the spirit and scope of the invention as described in the followingclaims.

What is claimed is:
 1. A method comprising: determining, at a mobiledevice, that a count of encounters by the mobile device with an accesspoint fails to satisfy a threshold, the access point associated with afirst network; and establishing a connection with a second network inresponse to determining the count fails to satisfy the threshold, theaccess point unassociated with the second network.
 2. The method ofclaim 1, wherein the count of encounters fails to satisfy the thresholdif a number of instances that the mobile device receives a signal fromthe access point within a particular time period is below the threshold.3. The method of claim 1, wherein establishing the connection with thesecond network comprises wirelessly connecting to a second access pointassociated with the second network.
 4. The method of claim 1, furthercomprising: receiving a signal from the access point at the mobiledevice; and incrementing the count in response to receiving the signal,wherein incrementing the count changes the count to an incrementedcount.
 5. The method of claim 4, further comprising: determining thatthe incremented count satisfies the threshold; and displaying, at themobile device, an indicator associated with the access point in responseto the incremented count satisfying the threshold.
 6. The method ofclaim 4, wherein the signal includes information identifying the accesspoint associated with the first network.
 7. The method of claim 4,wherein the signal is received during a first period of time, andwherein the count is incremented after the first period of time and inresponse to the signal being received during the first period of time.8. The method of claim 7, further comprising bypassing incrementing thecount during a second period of time that is subsequent to the firstperiod of time.
 9. The method of claim 8, further comprising, during thesecond period of time, receiving a second signal that includesinformation identifying the access point associated with the firstnetwork, wherein the count is not incremented in response to the secondsignal.
 10. The method of claim 1, further comprising: receiving userinput at the mobile device; updating a configuration to enable themobile device to establish a second connection with the access point inresponse to the user input indicating selection of a first option to usethe access point; and updating the configuration to disable the mobiledevice from facilitating establishment of the second connection with theaccess point in response to the user input indicating selection of asecond option to not use the access point.
 11. The method of claim 10,further comprising: displaying, at the mobile device, available accesspoints in response to the user input indicating selection of a thirdoption to display available access points; and stopping display of anindicator of available access points in response to the user inputindicating selection of a fourth option.
 12. The method of claim 1,further comprising determining that a second count of encounters by themobile device with a second access point satisfies the threshold, thesecond access point associated with the second network; and displaying,at the mobile device, a second indicator associated with the secondaccess point in response to the second count satisfying the threshold.13. The method of claim 1, wherein the second network provides access toanother network at a lower data rate than the first network.
 14. Themethod of claim 1, wherein the first network includes a cable network,and wherein the second network includes a cellular communicationsnetwork.
 15. A system comprising: a processor; and a memory, the memorystoring instructions that, when executed by the processor, cause theprocessor to perform operations including: determining, at a mobiledevice, that a count of encounters by the mobile device with an accesspoint fails to satisfy a threshold, the access point associated with afirst network; and establishing a connection with a second network inresponse to determining the count fails to satisfy the threshold, theaccess point unassociated with the second network.
 16. The system ofclaim 15, wherein the count of encounters fails to satisfy the thresholdif a number of instances that the mobile device receives a signal fromthe access point within a particular time period is below the threshold.17. The system of claim 15, wherein the operations further comprise:receiving a signal from the access point at the mobile device; andincrementing the count in response to receiving the signal, whereinincrementing the count changes the count to an incremented count.
 18. Acomputer-readable memory device storing instructions that, when executedby a processor, cause the processor to perform operations comprising:determining, at a mobile device, that a count of encounters by themobile device with an access point fails to satisfy a threshold, theaccess point associated with a first network; and establishing aconnection with a second network in response to determining the countfails to satisfy the threshold, the access point unassociated with thesecond network.
 19. The computer-readable memory device of claim 18,wherein the operations further comprise: determining that a second countof encounters by the mobile device with a second access point satisfiesthe threshold, the second access point associated with the secondnetwork; and displaying, at the mobile device, a second indicatorassociated with the second access point in response to the second countsatisfying the threshold.
 20. The computer-readable memory device ofclaim 18, wherein establishing the connection with the second networkcomprises wirelessly connecting to a second access point associated withthe second network.